System and method of providing contents for mobile communication terminal

ABSTRACT

A system and method of providing content for a mobile communication terminal are disclosed. In one embodiment, the method includes i) receiving package list data for content from a mobile communication terminal, wherein the content is organized into a plurality of individual files, and wherein the package list data comprises individual ID, size and version data of each of the individual files stored in the mobile communication terminal and ii) comparing, at a content server, at least one of the sizes and individual version data of at least two files having the same individual ID that are stored in the content server and mobile communication terminal. The method may further include transmitting at least one individual file stored in the content server to the mobile communication terminal, wherein the at least one individual file has individual file data different from the corresponding file indicated in the package list data.

RELATED APPLICATIONS

This application is a continuation application, and claims the benefitunder 35 U.S.C. §120 of U.S. patent application Ser. No. 11/724,698filed on Mar. 16, 2007, which is a continuation application, and claimsthe benefit under 35 U.S.C. §§120 and 365 of PCT Application No.PCT/KR2006/001369, filed on Apr. 13, 2006, both of which are herebyincorporated by reference in its entirety. PCT/KR2006/001369 alsoclaimed priority to and the benefit of Korean Patent Applications Nos.10-2005-0031232 and 10-2005-0031237 both filed in the KoreanIntellectual Property Office on Apr. 15, 2005, the entire contents ofwhich are incorporated herein by reference.

BACKGROUND

1. Field

The described technology generally relates to a system and a method ofproviding content for a mobile communication terminal, particularly, amethod of efficiently providing large-size content by organizing contentto be downloaded to a mobile communication terminal into a plurality ofsub-content files and for managing efficiently the large size content inthe mobile communication terminal.

2. Description of the Related Technology

Recently, the rapid development of Internet is enhancing access tovarious content data through the Internet.

The term “content” indicates various information or their contents, bothare provided over the Internet, such as text, music, games, movies, andexecutable program of reproducing the above-mentioned content on a userterminal.

The content was downloaded through the landline Internet and played ondesktop PCs or notebook computers in the past, however, since cellularphones or personal digital assistants (PDA) become popular nowadays, theneeds to use content over mobile communication terminals increase moreand more.

Currently, it becomes possible to provide several tens of mega-bytes toseveral giga-bytes content with ongoing advances in the technology ofmassive multimedia data transmission over the landline Internet andrapid performances of desktop PCs or notebook computers. However, inproviding content to a mobile communication terminal, it is the factthat small-size content can be sent to the mobile communication terminaldue to the limited memory volume, performance of the mobilecommunication terminal, and instability of wireless network.

Since small-size content used to be downloaded to the mobilecommunication terminal in the past, it was general to organize contentfor the mobile communication terminal as one file.

For example, in case of providing game content, execution data for usingcontent and resource data for presenting characters or backgrounds, etc.were put into one file and then provided.

Recently, it becomes possible to expand memory capacity of the mobilecommunication terminal with external memory devices and to improve itsprocessing performance, so that it allows to process large-size contentin the mobile communication terminal. It is, however, still the factthat large-size content is being provided in one file.

But, there may be the following shortcomings when providing content inone file to the mobile communication terminal.

First, in case of large-size content, there may be various patch filesafter the first development of content, and when content is provided inone file, whole content has to be newly downloaded for downloading arelatively small-size patch file.

Second, in case of downloading whole content to download a small sizepatch files, it causes increased communication costs due to high volumeof packet transmission through the network.

Third, in case of large size content, there may be an extension pack forexpanding function. In this case, even if there are many consistentcomponents between a basic pack of the content and the extension pack,whole extension pack has to be newly downloaded.

In addition, reproduction programs such as VOD player, DMB player, andMP3 player for mobile communication terminals have been included in anoperating system when manufacturing a mobile communication terminal dueto the performance of the terminal, however, it is possible to providepatch file for revising errors or extension pack for upgrading theseprograms through updating the terminal OS binary. But, since theperformance of the terminal is increasing continuously and thelimitation on the terminal storage is disappearing with external memorydevices, the possibility of downloading these kinds of programs used tobe provided with the terminal OS increases.

But, if this execution program is also downloaded in one file to themobile communication terminal, in case of downloading small size patchfiles or extension packs including lots of components that are alreadyincluded in the basic pack, there are still shortcomings that wholecontent has to be downloaded.

In addition, content for the mobile communication terminal has beenprovided in one file, and this file was stored in the predeterminedaddress region in memory of the mobile communication terminal as onefile without any specific directory.

Recently, it becomes possible to provide large size content due to theincreased performance of the mobile communication terminal and increasedmemory capacity, however, large size content is still provided to themobile communication terminal in one file and stored in thepredetermined storage region without designating any specific directory.

It is possible there are various patch files if the size of contentbecomes larger, however, whole content had to be downloaded for thesmall size patch file, and accordingly, the mobile communicationterminal must reserve large size of memory volume when downloadingcontent.

Also, no extension pack was provided for large size content that wasalready installed on the mobile communication terminal, or even if therewas an extension pack, this was recognized as a different file becausecontent was organized in one file, so that the memory volume was limitedbecause the extension pack was stored in another storage regiondifferent from the region where the basic pack was stored.

SUMMARY

One inventive aspect is a method of efficiently providing content for amobile communication terminal by organizing content into sub-contentfiles and a storage medium containing a program for performing themethod are disclosed.

Another aspect is a mobile communication terminal capable to managelarge size content efficiently and a storage medium containing a programfor implementing such a management of the large size content.

Another aspect is a method of providing content for a mobilecommunication terminal, comprising: storing content that is organizedinto sub-content files, wherein the sub-content files comprises at leastone of an executable file, a DLL file and a resource file; generatingpackage list data for the sub-content files; transmitting the packagelist data to the mobile communication terminal; and transmitting thesub-content files in the package list data to the mobile communicationterminal, wherein a download agent program in the mobile communicationterminal checks if the transmission of the sub-content files in thepackage list data completes.

Another aspect is a method of providing an individual file to the mobilecommunication system including a content server of providing content tothe mobile communication terminal, comprising: receiving package listdata for content stored in the mobile communication terminal, whereinthe content is organized into a plurality of individual files and thepackage list data comprises a content master ID and individual filedata; comparing the individual file data in the received package listwith the individual file data for the content stored in the contentserver; and transmitting one of individual files stored in the contentserver having different individual file data from the file in thereceived package list data to the mobile communication terminal.

Another aspect is a storage medium containing a program includinginstructions executable by a digital processing device of receivingindividual files of content for a mobile communication terminal from acontent server, said storage medium comprising: receiving latest packagelist data corresponding to the content stored in the mobilecommunication terminal from the content server, wherein the content isorganized into a plurality of individual files comprising at least oneof an executable file, a DLL file and a resource file, and the latestpackage list data comprises a content master ID, content unified versiondata, and individual file data; comparing individual file data in thelatest package list data with individual file data for the contentstored in the mobile communication terminal; and requesting for downloadof files among a plurality of individual files in the latest packagelist data having different individual file data from the file in themobile communication terminal to the content server.

Another aspect is a storage medium containing a program includinginstructions executable by a digital processing device of receivingextension pack files corresponding to basic packs of content pre-storedin a mobile communication terminal from a content server, said storagemedium comprising: receiving extension pack package list datacorresponding to the extension pack content from the content server,wherein the content is organized into a plurality of individual filescomprising at least one of an executable file, a DLL file and a resourcefile, and the extension pack package list data comprises a contentmaster ID, content unified version data and individual file data;comparing individual file data in the extension pack package list datawith individual file data for the content pre-stored in the mobilecommunication terminal; and requesting for download of files among aplurality of individual files in the extension pack package list datahaving different individual file data from the file corresponding to thebasic packs.

Another aspect is a storage medium containing a program includinginstructions executable by a digital processing device of managing largesize content for a mobile communication terminal to be downloaded from acontent server, said storage medium comprising: (a) receiving a packagelist for sub-content files consisting content from the content server,wherein the sub-content files comprises at least one of executable file,DLL file and resource, and the package list comprises a content masterID; (b) receiving the sub-content files; and (c) designating the contentmaster ID as a higher directory and storing each of the receivedsub-content files in lower directories of the content master ID,respectively.

Another aspect is a mobile communication terminal of managing large sizecontent, comprising: a downloading managing module, receiving a packagelist of sub-content files consisting content and sub-content files froma content server and storing the sub-content files based on a directorystructure, wherein the sub-content files comprises at least one ofexecutable file, DLL file and resource, and the package list comprises acontent master ID; and a memory volume checking module, checking whetheror not memory volume enough for the size of files to be transmitted bythe content server is reserved according to the existence of the contentmaster ID.

According to at least one of the disclosed embodiments, it becomespossible to transmit patch files of large size content individually byorganizing the content into sub-content files and managing thesub-content files with a package list.

According to at least one embodiment, it becomes possible to recover anessential file for execution, which a user deleted by mistake, through apatch process of content or request for re-downloading content, and totransmit both a game application that needs to be compiled and aresource file that does not need to be compiled at the same time.

Also, it becomes possible to manage large size content efficientlybecause the large size content that is organized into sub-content filesincluding files that can be shared commonly is stored in thepredetermined directory structure in the mobile communication terminal.

Furthermore, since a reception icon is displayed and the execution ofcontent that download of all latest patch files is not completed isprohibited during download of patch files, it is possible to use themobile communication terminal stably.

Moreover, during download of patch files, if download of one patch fileis completed, then the file that has same individual ID among thesub-content files is updated with the downloaded patch file, so thatthere is no need to reserve large memory volume.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a content providing system according to an embodiment.

FIG. 2 shows modules of the content server according to an embodiment.

FIG. 3 shows modules of the download agent program according to anembodiment.

FIG. 4 shows package list data according to an embodiment.

FIG. 5 shows configuration data of an executable file according to anembodiment.

FIG. 6 shows configuration data of a DLL file according to anembodiment.

FIG. 7 shows configuration data of a resource file according to anembodiment.

FIG. 8 shows configuration data of an item file according to anembodiment;

FIG. 9 is a flowchart showing the content download according to anembodiment.

FIG. 10 is a flowchart of downloading the required file according to anembodiment.

FIG. 11 shows modules of the download agent program according to anotherembodiment.

FIG. 12 is a flowchart of required file download procedure according toanother embodiment.

FIG. 13 shows the content providing system according to an embodiment.

FIG. 14 shows modules of the content manager according to an embodiment.

FIG. 15 shows the directory structure of content according to anembodiment.

FIG. 16 is a flowchart showing the storing procedure when downloadingcontent according to an embodiment.

FIG. 17 is a flowchart of icon displaying procedure in downloading patchfile according to an embodiment.

DETAILED DESCRIPTION

The aforementioned objects, features and advantages will be moreapparent from the following description in relation to accompanyingdrawings. In numbering elements in each drawing, same elements appearingon different drawings will have same reference number as possible.

Hereinafter, embodiments for providing content for a mobilecommunication terminal and the storage medium thereof will be describedin detail with reference to accompanying drawings.

FIG. 1 shows a content providing system according to an embodiment.

As shown in FIG. 1, the content providing system according to anembodiment may comprise a mobile communication terminal 100 and acontent server 108. The mobile communication terminal 100 and thecontent server 108 may be coupled to each other via network.

Here, the network may be a wireless network including BTS (BaseTransceiver Station), BSC (Base Station Controller) and PDSN (PacketData Serving Node).

The mobile communication terminal 100 can receive various kinds ofcontent after accessing wirelessly to the content server 108 by usingaforementioned network elements.

Generally, “content” usually indicates music data or movie data beingprovided over network such as Internet. However, in this specification,content further comprises an executable file of reproducing theabove-mentioned data and a link program (e.g., DLL program), so thatcontent in embodiments will indicate all data transmitted throughnetwork.

The mobile communication terminal 100 can be one of cellular phone, MBS(Mobile Broadcast System), and so on.

According to an embodiment, the mobile communication terminal 100comprises a wireless Internet browser 102, a download agent program 104and a content storage 106.

The wireless Internet browser 102 for reproducing a content list or anitem list being provided by the content server 108 can be one of WAP(Wireless Application Protocol) browser, ME (Mobile Explorer) and so on.

The download agent program 104 checks if the download of whole contentis performed in case of downloading content from the content server 108.

According to an embodiment, the content server 108 organizes contentinto several files (hereinafter, “sub-content files” or “pluralindividual files”) such as executable file (EXE file), link file,resource file (RES), item file, etc., rather than one file and storesthem. And, if a user requests for download, then the content server 108generates a package list comprising information of the sub-content filesand transmits the package list with sub-content files to the mobilecommunication terminal 100.

The executable file is continuously loaded on memory while certaincontent is reproducing.

The link file such as DLL (Dynamic Library Link) file is linked to theexecutable file that uses the link file during execution rather thancompiled with the executable file that is loaded onto memory of themobile communication terminal 100. The link file is for efficient use ofmemory, reuse of developed software, development for structuralsoftware, etc.

In addition, the resource file is for example a file for game graphic incase of game content, and a skin file in case of reproducing programsuch as VOD player.

The item file is for extending function of resource. For example, thisis an extension file of cars or tracks in racing game, or a file forskin change or skin extension in VOD player.

The package list data comprises a content master ID, unified versiondata, ID and version data of the executable file, and the number, ID andversion data of DLL, resource (RES) and item file included in thecontent.

According to an embodiment, the download agent program 104 receivespackage list data from the content server 108 and stores it. Also, incase of content transmission from the content server 108, the downloadagent program checks whether transmissions of each of sub-content files,which is included in the package list, are finished.

In addition, according to an embodiment, if there is a patch file foralready-downloaded content, the download agent program 104 of the mobilecommunication terminal 100 transmits package list data ofalready-downloaded content to the content server 108. The content server108 searches a file from the files currently stored in itself havingdifferent size or individual ID from the file in the mobilecommunication terminal 100 by using the package list data beingtransmitted from the mobile communication terminal 100, and thentransmits the searched file to the mobile communication terminal 100.

For example, if size or individual ID is not identical, it requirespatching or recovering a file that was deleted in the mobilecommunication terminal 100. In this case, the content server 108transmits the required file to the mobile communication terminal 100 byusing size data of individual file or individual version data.

According to another embodiment, it is possible for the mobilecommunication terminal 100 to make a decision whether or not a patchfile is needed. At this, the download agent program 104 receives thelatest package list of content from the content server 108, and comparesdata of individual files being included in the latest package list withdata of individual files being included in the mobile communicationterminal 100. After comparing, the download agent program 104 requeststhe download of files having different individual file data to thecontent server 108.

Here, different individual file data means, for example, that two fileshave same ID but different size or individual version. In this case, asit will be the patch file or recovery of deleted file, the downloadagent program 104 requests this to the content server 108.

As described above, according to an embodiment, large size content isorganized into sub-content files, and a providing process of patchfiles, etc., by using package list data is performed. Thus, it mayeliminate download of whole content for small size patch files ordeleted files.

The content storage 106 stores all kinds of content downloaded from thecontent server 108. The content storage 106 may be an internal memory ofthe mobile communication terminal 100 or an external memory for storinglarge-size content.

Although embodiments described the download of content via wirelessnetwork, they are not considered limiting, and downloading small sizepatch files via wireless network after downloading content on a user PCvia landline network and then moving the downloaded content to themobile communication terminal 100 may be also possible.

Database 110 is coupled to the content server 100 according to anembodiment, and database 110 stores user data, sub-content files thatconsist content, package list data and so on.

FIG. 2 shows modules of the content server according to an embodiment.

As shown in FIG. 2, the content server 108 according to an embodimentcomprises a content list providing module 200, a package list generatingmodule 202, a version comparing module 204, a size comparing module 206,a COD module 208, an encryption module 210, an application transmittingmodule 212, a resource transmitting module 214, and an authenticationkey providing module 216.

The content list providing module 200 provides a content list and itemlist to the mobile communication terminal 100 connected to the contentserver 108.

The package list generating module 202 generates the package list forsub-content files that include certain content.

The content server 108 according to an embodiment organizes content tobe downloaded to the mobile communication terminal 100 into sub-contentfiles, and generates a package list for these sub-content files.

FIG. 4 shows the package list data according to an embodiment. As shownin FIG. 4, package list data according to an embodiment comprises acontent master ID, a content unified version, the number of executablefiles, executable file configuration data, the number of DLL files, DLLfile configuration data, the number of resource files, resource fileconfiguration data, the number of item files, and item fileconfiguration data, etc.

The content unified version indicates that certain content is a basicpackage or an extension package and shows a patch version status.

According to an embodiment, the number of executable file may be one.Configuration data of executable file may comprise, as shown in FIG. 5,executable file ID, actual file name, version data, size and billingdata for one executable file.

Content unified version data can be represented in the form ofmajor/middle/minor such as 1.x.x or 2.x.x. The major number may be anidentification number for identifying basic package or extensionpackage, and middle and minor numbers may be for identifying patch.

In addition, the number of DLL files, resource files and item files mayvary with the kind of content. Each configuration data as shown in FIGS.6 to 8 comprises ID, version data, size and billing data of each file.

In addition, the item file is for extending resources and does not needto be included in the first download of content.

The package list generating module 202 according to an embodimentgenerates packet list having data of sub-content files on receiving thefirst content request of user and sends it to the content list providingmodule 200. The content list providing module 200 transmits the packagelist data to the mobile communication terminal 100.

Although the package list is generated after receiving contenttransmission request of user, it is just an example, and it is alsopossible to generate the package list beforehand and transmit it onreceiving user's request.

Then, when the downloading of sub-content files starts, the downloadagent program 104 of the mobile communication terminal 100 checks if allsub-content files included in the package list that was already providedis transmitted.

In addition, the package generating module 202 generates the latestpackage list not only in the first downloading of specific content butalso in downloading of patch file, etc., for content that was alreadystored in the mobile communication terminal 100.

According to an embodiment, the content server 108 comprises the versioncomparing module 204. The version comparing module 204 compares unifiedversion of content in the mobile communication terminal 100 with unifiedversion of content in the content server 108 to make a decision whetheror not a patch file is needed.

In addition, the individual file comparing module 206 compares data ofindividual files in the package list transmitted from the mobilecommunication terminal 100 with data of individual files in the packagestored in the content server 108.

As described above, the individual file according to an embodimentcomprises individual ID, size, version data and so on. The individualfile comparing module 206 compares size or individual version data oftwo files having same individual ID, each is stored in the contentserver 108 and the mobile communication terminal 100.

Through this, if individual file data is different, downloading of patchfile or deleted file to the mobile communication terminal 100 can beachieved.

Although an embodiment uses size data or individual version data, theindividual file comparing process may be performed by using various datarelating to individual file.

According to an embodiment, the content server 108 transmits a requiredfile list of content to the mobile communication terminal 100.

Here, the required file list indicates a list of files to be downloadedto the mobile communication terminal 100, which is identified throughthe comparison of individual file data.

After transmitting the required file list, the transmission process ofthe required file (including patch file or recovery file) is performed,and the download agent program 104 of the mobile communication terminal100 checks whether or not the transmissions of all required file arefinished.

Thus, since the user can download individual files to be patched orrecovered among sub-content files that consist one content, the wirelessnetwork access time will decrease and, as a result, communicationexpense will be reduced.

COD module 208 compiles executable files and DLL files needed to becompiled among sub-content files.

The COD module 208 is a key component of WIPI (Wireless InternetPlatform for Interoperability) for the wireless Internet platformstandard under discussion.

According to an embodiment, executable files or DLL files amongsub-content files forming content need to be complied, and the CODmodule 208 compiles such files.

The encryption module 210 encodes each sub-content file if necessary.

The executable files and DLL files are compiled and then encoded in theCOD module 208 as described above, and the resource files and item filesare encoded without being compiled.

Also, according to an embodiment, each of DLL files, resource files anditem files can be organized into plural files, and the encoding processcan be applied to each file individually, if necessary.

The game application transmitting module 212 transmits executable filesand DLL files among sub-content files to the mobile communicationterminal 100. Namely, the game application transmitting module 212transmits the compiled files such as executable files and DLL files thatthe COD module 208 compiled.

The resource transmitting module 214 transmits resource files and itemfiles, both do not need to be compiled, to the mobile communicationterminal 100.

The item file is for extension of resource, and as described above,includes graphic expression extension of game, additional skin of eachplayer, etc. The item file is not an essential file to be downloaded atthe first content download.

When carrier provides content in the past, whole files were compiledinto one file and then the compiled file was transmitted. But, in thiscase, carrier who operates the content server could not provide filesthat were not compiled at one time.

According to an embodiment, since it becomes possible to transmit eachof compiled file and resource file that is not needed to compileindividually, it allows for carrier to transmit sub-content files at onetime.

The authentication key providing module 216 transmits an authenticationkey for decoding the encoded files for content protection to the mobilecommunication terminal 100.

In the above, although it was described that each module in the contentserver 108 provides content according to the user's request, it is justan example, and each module can be performed by separate servers.

FIG. 3 shows modules of the download agent program according to theembodiment.

As shown in FIG. 3, the download agent program according to anembodiment comprises a transmission completion determining module 300, apackage list transmitting module 302, and a required file list receivingmodule 304.

The transmission completion determining module 300 checks that downloadof all sub-content files included in the package list being sent fromthe content server 108 is completed on the first download of content.

When transmitting sub-content files that consist one content, thetransmission completion determining module 300 checks the transmissioncompletion of each file by using size of the corresponding file that wasalready provided. The transmission completion determining module 300 cansend a transmission completion response signal to the content server 108when transmission of individual file completes, and a transmissioncompletion response signal for entire files when transmission of allsub-content files completes.

But, this is just an example, and it is possible to send the responsesignal when the transmission of all sub-content files completes.

In addition, the transmission completion determining module 300 checksthe transmission completion when downloading required files.

As described above, according to one embodiment, if patch file orrecovery file for content that was already downloaded to the mobilecommunication terminal 100 is required, the content server 108 generatesa required file list and transmits it. At this time, the transmissioncompletion determining module 300 checks the transmission of allindividual files completes by using the required file list.

If there is an inquiry request for patch file of specific content fromthe mobile communication terminal 100, the content server 108 needspackage list data for the specific content that is stored in the mobilecommunication terminal 100 to compare individual file data. For this,the package list transmitting module 302 transmits the package list datathat is stored in the mobile communication terminal 100 to the contentserver 108.

The required file list receiving module 304 receives a required filelist that the content server 108 generates by comparing individual filedata in the package list transmitted from the mobile communicationterminal 100 with individual file data that is currently stored in thecontent server 108.

FIG. 9 is a flowchart showing the content download according to anembodiment.

FIG. 9 shows the procedure for the first downloading of content, andthis procedure can be applied to not only the download of basic pack ofcontent but also the download of extension pack.

Referring to FIG. 9, the mobile communication terminal 100 requests acontent list to the content server 108 (S900).

The content server 108 transmits the content list as a response to themobile communication terminal 100, and the wireless Internet browser 102of the mobile communication terminal 100 receives the content list anddisplays (S902).

When the user selects desired content to be downloaded, the mobilecommunication terminal 100 requests the download of the selected contentto the content server 108 (S904).

Then, the content server 108 extracts sub-content files that consist therequested content from database 110 (S906) and generates a package list(S908).

As described above, the package list comprises content master ID,unified version data, each number and configuration data of executablefiles, DLL files and resource files.

The content server 108 transmits the generated package list data to themobile communication terminal 100 (S910), and then transmits sub-contentfiles that consist one content (S912).

The download agent program 104 of the mobile communication terminal 100checks whether or not transmission of all sub-content files completes byusing the package list data transmitted from the content server (S914).

If transmission of all sub-content files completes, the mobilecommunication terminal 100 transmits a transmission completion signal tothe content server 108 (S916), and the content server 108 transmits aresponse signal to the mobile communication terminal 100 (S918).

FIG. 10 is a flowchart of downloading the required file according to anembodiment.

FIG. 10 shows the procedure of downloading individual files after thefirst downloading of content, and referring to FIG. 10, the mobilecommunication terminal 100 accesses to the content server 108 andtransmits package list data stored in the mobile communication terminal(S1000).

According to an embodiment, the package list data may comprise contentmaster ID, IDs of each individual file, individual file size, versiondata and so on.

The content server 108 receives a package list from the mobilecommunication terminal 100, and compares individual file data stored inthe content server 108 with individual file data in the received packagelist (S 1002).

The content server 108 generates a required file list indicating fileshaving different individual file data (S1004).

As described above, the required file list means a list of files, i.e.,patch files and recovery files that have same individual ID butdifferent size or individual version.

The content server 108 transmits the required file list to the mobilecommunication terminal 100 (S1006), and then transmits individual filesincluded in the required file list (S1008).

The mobile communication terminal 100 checks that transmission of allfiles included in the required file list completes (S1010).

If the transmission of all patch files completes, the mobilecommunication terminal 100 transmits a file transmission completionsignal to the content server 108 (S712), and the procedure ofdownloading individual files finishes when the content server 108transmits a response signal thereto (S1014).

As this, according to an embodiment, it becomes possible to download therequired file by organizing content into sub-content files and comparingindividual file data.

In addition, according to an embodiment, the required file downloadprocedure may be performed by the download agent program 104 thatautomatically accesses to the content server 104 to check if there ispatch files when downloading content according to the predeterminedmethod, or by an individual program, the target of patch and executableon the mobile communication terminal. that calls a download agentprogram through API, or by a re-download request from the user.

In addition, although an embodiment described the procedure ofdownloading required files or recovery files, it is also possible toselectively transmit files that are added to the extension pack by theaforementioned version comparison and size comparison process during theprocedure of downloading the extension pack corresponding to the basicpack that is already stored in the mobile communication terminal 100.

FIG. 11 shows modules of the download agent program according to anotherembodiment.

According to another embodiment, when downloading the required file, thecomparison process of individual file data is performed by the mobilecommunication terminal 100.

For this, as shown in FIG. 11, the download agent program according toan embodiment may comprise a transmission completion determining module1100, a package list transmitting module 1102, a latest package listreceiving module 1104, an individual file comparing module 1106, and arequired file requesting module 1108.

Since the transmission completion determining module 1100 is same to theone that was already described in FIG. 3, description about this will beomitted here.

The package list transmitting module 1102 is same to the one that wasalready described in FIG. 3, however, the process of selecting therequired file is performed by the mobile communication terminal 100 inanother embodiment.

It is not necessary for the package list data to include all data ofsub-content files, and it is possible to include content mast ID, whichis for the content server 108 to identify content that the mobilecommunication terminal 100 requests.

When receiving the package list including the content mast ID from themobile communication terminal 100, the content server 108 generates thelatest package list corresponding to the content master ID and transmitsit to the mobile communication terminal 100. At this time, the latestpackage list receiving module 1104 receives the latest package list fromthe content server 108.

The individual file comparing module 1106 compares data of individualfiles in the latest package list being transmitted from the contentserver 108 with data of individual files in the mobile communicationterminal 100.

As described above, comparison of individual files is to compare size orindividual version data of two files having same individual ID, however,it is not limited to these data.

Through the individual file comparing process, the required file to bedownloaded from the content server 108 can be identified, and therequired file requesting module 1108 requests the download of therequired file to the content server 108.

FIG. 12 is a flowchart of a required file download procedure accordingto another embodiment.

Referring to FIG. 12, the mobile communication terminal 100 extracts apackage list including the content master ID and transmits it to thecontent server 108 (S1200).

The package list transmission process can be performed by an automaticrequest of the download agent program if content is executed in themobile communication terminal 100. But, it also can be performed by anexecuted content request for the existence of patch files by callingAPI, or by a content re-download request of the user.

After identifying the content master ID, the content server 108generates the latest package list by extracting sub-content filescorresponding to the content master ID (S1202). The content server 108transmits the latest package list to the mobile communication terminal100 (S1204).

The mobile communication terminal 100 compares data of individual filesin the latest package list with data of individual files in the mobilecommunication terminal 100 (S1206).

At this time, since individual files having different data are the fileto be downloaded from the content server 108, the mobile communicationterminal 100 requests download of the file to the content server 108(S1208), and the content server 108 transmits the corresponding patchfile as a response thereto (S1210).

The mobile communication terminal 100 checks whether or not transmissionof all required file completes by using the latest package list (S1212),and if completes, then transmits a patch file transmission completionsignal to the content server 108 (S1214).

When the content server 108 transmits a response signal for the patchfile transmission completion signal, the download of patch file finishes(S1216).

FIG. 13 shows the content providing system according to an embodiment.

When comparing FIG. 13 with FIG. 1, since the composition of the mobilecommunication terminal 100 is the same, excepting comprising a contentmanager 1300, description on the other components will be omitted.

As described above, the mobile communication terminal 100 according toan embodiment receives package list data and corresponding sub-contentfiles from the content server 108.

The package list data, as shown in FIG. 4, may comprise content masterID, unified version data, ID and size of executable file, and thenumber, ID and size of DLL files, resource files and item files.

Here, the content master ID is an identifier for the content server 108or the mobile communication terminal 100 to identify content. Thecontent unified version indicates that certain content is basic packageor extension package and shows a patch version status.

The content unified version data according to an embodiment can berepresented in the form of major/middle/minor such as 1.x.x or 2.x.x.The major number is an identification number for identifying basicpackage or extension package. Middle and minor numbers are foridentifying patch.

In addition, the number of DLL files, resource files and item files mayvary with the kind of content. And each configuration data as shown inFIGS. 5 to 8 comprises individual ID, version data, size and billingdata of each file.

If the content server 108 transmits content, the content manager 1300according to an embodiment checks if the transmission of all filesorganizing content is completed by using a package list that the contentserver generated.

As described above, content according to an embodiment is organized intosub-content files, which are independent to each other. The contentmanager 1300 stores files under download in the form of a temporaryfile, then renames and stores the file as an executable file if thedownload of files completes.

At the first time of receiving content, the content manager 1300generates a folder for content under download by using the contentmaster ID in a content storage, and stores sub-content files, thatorganize content, in lower directories of the content master ID folder,respectively.

FIG. 15 shows the directory structure of content according to oneembodiment. As shown in FIG. 15, the content master ID is a higherdirectory, and sub-content files such as executable file, icon file,content basic data file, DLL file and resource file are stored in lowerdirectories.

Here, the icon file comprises receiving icon data and execution icondata.

In addition, if receiving the extension pack or patch file of content,content to be extended or patched is already stored in the mobilecommunication terminal 100. In this case, the content manager 1300stores files of the extension pack or patch file in lower directories ofthe content master ID where these files are already stored.

As described above, since content according to an embodiment isorganized into several independent sub-content files, a patch file canexist independently to each sub-content file.

Thus, if receiving more than one patch file, the content manager 1300according to an embodiment 1300 overwrites the patch file to the filethat is already stored in the mobile communication terminal 100.

Each sub-content file according to an embodiment comprises individual IDdata. Thus, the content manager 1300 updates a file having sameindividual ID of the patch file among the already stored files to thepatch file

Generally, in downloading files the content server 108 checks first thatthe mobile communication terminal 100 can receive the volume of contentto be downloaded and then starts to transmit. According to anembodiment, in transmitting new patch files, if the mobile communicationterminal 100 reserves memory volume equal to the patch having thelargest size rather than the total volume of patch files, then it ispossible to receive patch files.

Namely, since content was organized into one file, total content must bedownloaded even if there was a patch file. Thus, the mobilecommunication terminal had to reserve the memory volume equal to thesize of total content. But, according to an embodiment, content isdivided into small size sub-content files, and each of these files isoverwritten independently after its download completes. By this, itbecomes possible to receive the patch file even if small memory volumeis reserved.

Also, in case of extension pack, some of sub-content files forming theextension pack may be identical to some of sub-content files that arealready stored in the mobile communication terminal 100. In downloadingthe extension pack, it is possible to download patch files that are notincluded in the basic pack or have different size from the sub-contentfiles forming the basic pack.

The content storage 106 stores all kinds of content downloaded from thecontent server 108. The content storage 106 may be an internal memory ofthe mobile communication terminal 100 or external memory for storinglarge-size content.

FIG. 14 shows modules of the content manager according to an embodiment.

As shown in FIG. 14, the content manager according to an embodimentcomprises a download managing module 1400, an icon displaying module1402, a launching module 1404, and a memory volume checking module 1406.

The download managing module 1400 manages the download of sub-contentfiles that the content server 108 is transmitting. The download managingmodule 1400 checks whether or not the transmission of all sub-contentfiles completes by using package list data that the content server 108transmitted.

Also, in case of receiving sub-content files, the download managingmodule checks that a content master ID of a sub-content file indownloading is already stored in the content storage 106. If there is nocontent master ID of the sub-content file, then this is regarded as thefirst download, and thus a new fold may be generated under the name ofthe content master ID and the received sub-content files are stored inlower directories of the content master ID.

On the other hand, if this is not the first download, namely, in case ofreceiving the extension pack or patch file, the download managing module1400 stores newly added files in the extension pack (i.e., not includedin the basic pack) or patch files in lower directories of the contentmaster ID in the content storage 106.

As describe above, since the file to be patched is already stored in thecontent storage 106 in case of patch file, the download managing module1400 updates the stored files with the patch file when receivingindividual patch file.

Also, in case of extension pack, some of sub-content files formingextension pack will be identical to the sub-content files (i.e., formingthe basic pack) that are already stored in the mobile communicationterminal 100. The download managing module 1400 overwrites the file thatis one of extension packs and has same individual ID of the sub-contentfile in the basic pack patch file, and stores the file (i.e.,newly-added file) that is not included in the basic pack in the lowerdirectory of the content master ID.

The icon displaying module 1402 displays icons corresponding to content,and the icon according to an embodiment may be classified into executionicon and receiving icon.

Here, the execution icon indicates that it is possible to executecontent corresponding to the icon, and if a user selects the executionicon, then content is executed.

But, the receiving icon indicates that plural individual files forcontent are under download, so that content is not executed when a userselects the receiving icon.

Also, if the transmission of patch files was suspended previously, thereceiving icon lets the user to recognize that a continuous download isneeded. Also, if the user selects the receiving icon after thetransmission of patch files is suspended, the continuous download ofpatch files may be performed automatically.

In embodiments, when the transmission of patch files is suspended, someof sub-content files consisting content may be files corresponding tothe updated unified version, some may be files corresponding to theprevious unified version. In this case, there may be an error inexecuting content if the user executes content, so that the receivingicon has to be displayed.

The launching module 1404 transmits content basic data to the contentserver 108 to initiate the patch file transmission procedure forspecific content.

Here, the content basic data comprises the content master ID that istransmitted from the content server 108 and content unified versiondata.

When requesting the existence of patch files to the content server 108,the mobile communication terminal 100 transmits content basic data tothe content server 108. The content server 108 transmits the latestpackage list that is currently stored in the content server 108 to themobile communication terminal 100 by the content master ID. If unifiedversion data in the received latest package list is different fromunified version data of content in the mobile communication terminal100, the mobile communication terminal 100 will recognize that patchfile is needed. As this, in case of different version, the mobilecommunication terminal requests the download of files having differentsize to the content server 108 by comparing sizes of each sub-contentfile in the package list with sizes of each sub-content file in themobile communication terminal 100.

The procedure of comparing the unified version and size may be performedin the content server 108.

When the content server 108 inquires that the mobile communicationterminal 100 reserves the memory as much as the size of content to bedownloaded, the memory volume checking module 1406 checks the remainingmemory volume of the mobile communication terminal 100.

At this time, if the remaining memory volume is less than the size ofcontent to be downloaded, then transmission of content will not beperformed.

In addition, according to an embodiment, in case of receiving patchfiles, the download managing module 1400 overwrites the received patchfile on the existing file whenever transmission of each patch filecompletes. Thus, there is no need to reserve the memory volume for allpatch files, but the memory volume for the largest patch file. Also,since there will be a file identical to the file in the basic pack incase of downloading the extension pack, it is also possible to downloadthe patch file or extension pack if the memory volume for files neededto be patched and files not included in the basic pack is reserved.

FIG. 16 is a flowchart showing the storing procedure when downloadingcontent according to one embodiment.

Referring to FIG. 16, when downloading content, the mobile communicationterminal receives a package list from the content server 108 (S1600).

When receiving the package list, the mobile communication terminal 100extracts a content master ID from the package list and checks whether ornot there is the content master ID in the content storage 106 (S1602).

As it is download of new content if there is no content master ID, themobile communication terminal 100 checks if there is enough memoryvolume, equal to the size of all sub-content files that consist contentin the content storage 106 (S1604).

If the reserved memory volume is not enough to the size of allsub-content files, then the content download procedure finishes,otherwise, the step of generating a folder, under the higher directorywith name of the content master ID will be performed (S1606).

Then, the file download procedure initiates, and the mobilecommunication terminal 100 stores one of sub-content files in the stateof being downloaded from the content server 108 in the form of atemporary file (S1608) and checks that the transmission of individualfiles completes by using size data of the file under download (S1610).

If the transmission of individual files completes, these files will bestored in the lower directories of the content master ID (S1612).

On the other hand, if there is the content master ID at the above step(S602), i.e., under download of patch files or extension packs, themobile communication terminal 100 checks whether or not the memoryvolume, equal to the size of the largest file that is one of patch filesto be downloaded is reserved (S1614).

If the memory volume for the largest file among patch files is reserved,the procedure of receiving patch files may be performed, and at thistime, since a folder having the name of the content master ID for thepatch file is already exist, the file under the transmission from thecontent server 108, which is not completely transmitted, will be storedin the form of a temporary file without generating a folder (S1616).

Then, after checking whether or not the transmission of individual filecompletes (S1618), if the transmission of individual files completes,the mobile communication terminal 100 checks if there is a file amongthe files stored in the mobile communication terminal 100 having ID samewith the transmission completed file (S1620).

At this time, as it indicates that the transmission completed file ispatch file if there is the file having same ID, the step of overwritingthe existing file will be performed (S1622), and as it indicates thatthe transmission completed file is an additional file if there is nofile having same ID, the step of storing the file in the lower directoryof the content master ID will be performed (S1612).

FIG. 17 is a flowchart of the icon displaying procedure duringdownloading patch files according to one embodiment.

Referring to FIG. 17, if receiving the patch file (S1700), the icondisplaying module in the mobile communication terminal 100 displays areceiving icon (S1702).

Then, the completion of path file transmission is checked (S1704), andif the transmission of patch files completes, an execution icon will bedisplayed (S1706).

But, if the transmission of patch files is not completed at the abovestep (S704), namely, if there is a suspension on the transmission ofpatch files, the receiving icon will be maintained (S1708).

Then, if there is an icon selection signal by a user's request (S1710),the mobile communication terminal 100 requests the continuous downloadfor the suspended file to the content server 108 (S1712).

Although in embodiments, the receiving icon is displayed when receivingpatch files In the above, they are considered limiting, and it is alsopossible to display an icon when downloading extension packs forprohibiting a user from executing content.

Also, it is also possible to apply the aforementioned procedure to therecovery file transmission to recover the file that the user deleted aswell as the patch file transmission for updating the existing files.

While the disclosed embodiments have been described with reference tothe accompanying drawings, it is appreciated that they are notconsidered limiting, and those who skilled in the art will understandthere will be many of alternatives, changes, and addition, and thesealternatives, changes, and addition will be included within the scope ofthe following claims.

1. A method of providing content to a mobile communication terminal, themethod comprising: receiving package list data for content from a mobilecommunication terminal, wherein the content is organized into aplurality of individual files, and wherein the package list datacomprises individual ID, size and version data of each of the individualfiles stored in the mobile communication terminal; comparing, at acontent server, at least one of the sizes and individual version data ofat least two files having the same individual ID that are stored in thecontent server and mobile communication terminal; and transmitting atleast one individual file stored in the content server to the mobilecommunication terminal, wherein the at least one individual file hasindividual file data different from the corresponding file indicated inthe package list data.
 2. The method of claim 1, further comprising:producing a required file list of files having different individual filedata; and transmitting the required file list to the mobilecommunication terminal, wherein the required file list is configured tocontrol a download agent program of the mobile communication terminal tocheck if the transmission of all required files is complete.
 3. Themethod of claim 1, wherein the individual files are sub-content filesassociated with the content, wherein the sub-content files areclassified according to file types, and wherein the file types comprisean executable file, a dynamic library link (DLL) file and a resourcefile.
 4. A method of providing content in a mobile communicationterminal, the method comprising: receiving latest package list data forcontent from a content server, wherein the content is organized into aplurality of individual files, and wherein the latest package list datacomprises individual file data for the individual files stored in thecontent server; comparing, at a mobile communication terminal, theindividual file data contained in the latest package list data withindividual file data for the individual files stored in the mobilecommunication terminal; and requesting downloading of at least one ofthe individual files indicated in the latest package list data from thecontent server, wherein the at least one individual file has individualfile data different from the corresponding file stored in the mobilecommunication terminal.
 5. The method of claim 4, wherein the comparingis performed before the requesting of the downloading.
 6. The method ofclaim 4, wherein the individual files are sub-content files associatedwith the content, wherein the sub-content files are classified accordingto file types, and wherein the file types comprise an executable file, adynamic library link (DLL) file and a resource file.
 7. The method ofclaim 4, wherein the individual file data comprises individual ID, sizeand version data of each of the individual files, and wherein thecomparing comprises comparing at least one of the sizes and individualversion data of at least two files having the same individual ID thatare stored in the content server and mobile communication terminal.
 8. Amethod of providing content in a mobile communication terminal, themethod comprising: receiving extension pack package list data forcontent from a content server, wherein the content is organized into aplurality of individual files, and wherein the extension pack packagelist data comprises individual file data for the individual files storedin the content server; comparing, at a mobile communication terminal,the individual file data contained in the extension pack package listdata with individual file data for individual files stored in the mobilecommunication terminal; and requesting downloading of at least one ofthe individual files indicated in the extension pack package list datafrom the content server, wherein the at least one individual file hasindividual file data different from the corresponding file stored in themobile communication terminal.
 9. The method of claim 8, wherein thecomparing is performed before the requesting of the downloading.
 10. Themethod of claim 8, wherein the individual files are sub-content filesassociated with the content, wherein the sub-content files areclassified according to file types, and wherein the file types comprisean executable file, a dynamic library link (DLL) file and a resourcefile.
 11. The method of claim 8, wherein the individual file datacomprises individual ID, size and version data of each of the individualfiles, and wherein the comparing comprises comparing at least one of thesizes and individual version data of at least two files having the sameindividual ID that are stored in the content server and mobilecommunication terminal.